If I create a Lync meeting in Outlook, and then click on the URL to start the meeting, I get"

"an error occurred during the Lync Meeting"

If I cut and paste the URL into a browser, the meeting starts fine.

The only error I see on the Lync Client log is a HRREULT="0x80f10041" for the Meet. URL.

Any

Interesting note:

If I change meeting option from dedicated meeting to "A new meeting space", then the linc works.

If I change it back, then the linc stops working again.

Could the sync between what Oultook generates and what the server supports, be broken?

Hi,

What's version of outlook and lync you are using?

Please install the latest update for the Lync client the check the issue again:

http://technet.microsoft.com/en-us/lync/gg131945

Outlook 2013

Lync 2013

Exchange 2010

Lync Server 2010

I will check for updates.

hi,

we have same issue and I have checked the server and client both are updated with current patch's the issue is remain.

Abhishek jangid

Has to be IE10 issue.

Works fine in Firefox and Chrome.

We loaded latest patches to Lync Server and Client 2010.  No effect.

I think IE10 works fine, unless I am accessing something from Microsoft, then it usually fails. (forums, licensing site, Xbox site, FOPE site and now my internal Lync server)

I have same issue..

In Windows Server 2008 R2 and Windows 7, Lync meeting Can running well. But In Windows 8 and windows server 2012, Lync meeting fail.

Any update to resolve this problem ?

Thanks,

EJ

Hi

I had the same problem

In my case - Disabling of the "Symantec Endpoint Protection" Outook add-in solved my problem.

I'm experiencing the same issue, I do not have odd plug ins enabled in outlook 2013.  I am running the latest lync 2013 client with November updates.

If I copy the URL and paste in browse it works or if I right click the "Join Lync Meeting" shortcut and choose open url it works, it will even open when clicking join lync meeting on the menu bar.

Is this a known bug?

• Edited by Steve_710 Wednesday, November 13, 2013 5:16 PM

I still see this error in our environement, any suggestions?